This is the list of addresses you are using. You may have up to 11 addresses and the order is important! The first address listed *should* be your primary address, followed by your AKA addresses. QECHO uses the closest address system when tossing mail. This will be used to generate the NODE statement needed by Qecho. ! This allows the BBS to use the message base while exporting and tossing mail (you must use SHARE). ! The ARCHIVER statement allows you to set the default archiver QECHO will use to archive echomail to outbound systems. This can be overridden by the 'PACKERS' 'ENDPACKERS' statement. If this line is omitted, 'PKPAK -OCT -A' will be used. Qecho Manager will allow you to use either a default or enter your own command line. The default may not be what you want to use. For example, Zoo is set up for v2.10 and won't work with earlier versions and Arc is set up to use Pak. Only one Archiver statement is allowed. If you try to enter a second statement, it will replace the first. A blank line can be entered but it will remove the archiver statement and you will be using PKPAK -OCT -A (not very efficient). These statements allow you to tell QECHO the archiver to use for a certain address. Below is an example: PACKERS 1:300/11.1 PKZIP -A 1:300/12 PKZIP -A 1:300/8 PKPAK -O -A 1:300/20 PKZIP -A 1:300/2.2 PKZIP -A ENDPACKERS Note: In this example, if you don't have the default archiver set, I would recommend using ARCHIVER PKZIP -A. Then you can just define PKPAK for 1:300/8 and save typing.:-) This statement allows you to strip SEEN-BYS on all echomail exported across ZONES. ! Control over ARCHIVERS that QECHO uses is fully configurable. These statements allow you to choose QECHO's DEARC string for each supported archiver. You may use PAK 2.51 to unZIP, etc. The default settings below are what QECHO used before v2.75. ZIP PKUNZIP/ON ZOO ZOO EO LHARC LHARC E /M PAK PAK E /WA ARC PKUNPAK/R PKPAK PKUNPAK/R ! A POINTNET function is used in cases when you can't use true 4D addressing. If one of your points is using an older echo- mail program, it probably doesn't understand 4D addressing. To set up POINTNET: For two points, use the node statement 'nnnn/n and nnnn/n', where 'nnnn' is your pointnet address and 'n' is the address of each point. The points must address you using the first address in this control file. You'll also need to place the statement 'BOSSNODE' in the control file. BOSSNODE POINTNET 2400 This path points to the directory QECHO will put the packets it creates during runtime. If not defined, QECHO will create the packets in your system directory. Example: PACKETPATH F:\TEMP ! This is the directory that QECHO will put its AREAS.KDP file to keep track of duplicate messages. Example: KDP-PATH F:\TEMP ! This command will generate a log file (QECHO.LOG). ! This is the directory that QECHO will write the logfile. If this is omitted, QECHO will write to the current directory. Example: LOGPATH F:\TEMP ! Specifies DOS path where duplicate messages will be placed. If omitted duplicate messages will NOT be saved. ! Specifies the DOS path where network mail is stored in .MSG file form. This is required. ! Specifies the DOS path the mailer places inbound files. This is required. ! Specifies the DOS path where QECHO will put outbound archive files. This should never be the same as the FILESPATH! This is required when using the -A commandline switch. ! Specifies the DOS path the oMMM outbound bundle area is. Only used if your system runs oMMM to archive mail (Binkley). This is required if using the -Z command line switch. ! Specifies DOS path QuickBBS system files are stored (message base files, configuration file). This is required if you use the -T command line switch. ! This limits the size of the .pkt files. 0 will make unlimited size packets. Example: PACKETSIZE 512 In most cases, either leave this blank or make it 0. !
